Fixes: https://gitlab.com/buildroot.org/buildroot/-/issues/55

When gcc sees a linker option (-Wl,..) it executes the linker, leading to
confusing error messages if no source files are provided, E.G.:

% gcc
gcc: fatal error: no input files
compilation terminated.

% gcc -Wl,-z,now
/usr/bin/ld: /usr/lib/gcc/x86_64-linux-gnu/12/../../../x86_64-linux-gnu/Scrt1.o: in function `_start':
(.text+0x17): undefined reference to `main'
collect2: error: ld returned 1 exit status

It is not really trivial to detect in the wrapper if linking will be done,
but we can at least check if any non-option arguments (E.G.  source/object
files) are passed and skip the -Wl,.. options if not.

% ./host/bin/aarch64-linux-gcc
aarch64-linux-gcc.br_real: fatal error: no input files
compilation terminated.

With this fixed we no longer need the special case for --help -v from commit
9954315 ("toolchain/toolchain-wrapper: make gcc --help -v work
correctly"), so drop that.

Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Building Python for the target requires host Python via
PYTHON3_DEPENDENCIES. Host Python is exposed as a standalone Kconfig
option, so when BR2_PACKAGE_PYTHON3=y, it is possible for host Python to
be built even when BR2_PACKAGE_HOST_PYTHON3=n. Normally this is OK for
host packages. However, host-python3 has a number of sub-options, which
sometimes need to be selected by a package. In that case, that
particular package has to add the `select BR2_PACKAGE_HOST_PYTHON3`
while it doesn't have a direct dependency on host-python3.

Add `select BR2_PACKAGE_HOST_PYTHON3' to python3 itself.

Signed-off-by: Liam Hupfer <lhupfer@xes-inc.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

BR2_PACKAGE_HOST_PYTHON3 is now selected by python3 itself, which is a
direct dependency. The select was only needed to be able to select
BR2_PACKAGE_HOST_PYTHON3_SSL.

Remove the redundant `select BR2_PACKAGE_HOST_PYTHON3`.

Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

BR2_PACKAGE_HOST_PYTHON3 is now selected by python3 itself, which is a
direct dependency. The select was only needed to be able to select
BR2_PACKAGE_HOST_PYTHON3_SSL.

Remove the redundant `select BR2_PACKAGE_HOST_PYTHON3`.

Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

The nvidia BlueField-3 DPU includes Arm Cortex-A78 Hercules
processors. See [1].

The Cortex-A78 support was added in Buildroot in commit [2].

This commit adds BR2_cortex_a78=y in nvidia_bf3_defconfig to enable
optimisations for this processor.

[1] https://www.nvidia.com/en-us/networking/products/data-processing-unit/
[2] https://gitlab.com/buildroot.org/buildroot/-/commit/f4690c2bfd7d51c614d09ff470e725c795bab980

Cc: Vincent Jardin <vjardin@free.fr>
Tested-by: Vincent Jardin <vjardin@free.fr>
Signed-off-by: Julien Olivain <ju.o@free.fr>

Signed-off-by: Julien Olivain <ju.o@free.fr>
Reviewed-by: Vincent Jardin <vjardin@free.fr>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

- Move URL to slicer69. This is where any releases past 3.04 are.
  - Continue to use the tar.xz archives.

See doc/Changelog for details.

Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

The Open Home Foundation generously sponsored the Buildroot project
end of 2024, credit them.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Commit bdcdc44 got the div soup
wrong, adjust this.

Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>

Add new defconfig for STMicroelectronics board STM32MP135F-DK.

STM32MP135F-DK features can be found here:
  https://www.st.com/en/evaluation-tools/stm32mp135f-dk.html

Signed-off-by: Raphael Gallais-Pou <rgallaispou@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

For change log since v0.3.28, see:
https://github.com/OpenMathLib/OpenBLAS/releases/tag/v0.3.29

Signed-off-by: Julien Olivain <ju.o@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Release notes:
https://github.com/jirka-h/haveged/releases/tag/v1.9.19

Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

License hash changed due to year update.

Release notes:
https://github.com/NetworkConfiguration/dhcpcd/releases/tag/v10.1.0
https://github.com/NetworkConfiguration/dhcpcd/releases/tag/v10.0.10
https://github.com/NetworkConfiguration/dhcpcd/releases/tag/v10.0.9

Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

- License hash changed due to year update.
- Updated site to new location.

Release notes:
https://github.com/smuellerDD/jitterentropy-library/releases/tag/v3.6.1
https://github.com/smuellerDD/jitterentropy-library/releases/tag/v3.6.0
https://github.com/smuellerDD/jitterentropy-library/releases/tag/v3.5.0

Changelog file:
https://github.com/smuellerDD/jitterentropy-library/blob/v3.6.1/CHANGES.md

Signed-off-by: Akhilesh Nema <nemaakhilesh@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

Since Buildroot commit [1] "package/e2fsprogs: bump version to
1.47.2", running the runtime test tests.fs.test_ext.TestExt2 with the
command:

    utils/docker-run support/testing/run-tests \
        -d dl -o output_folder \
        tests.fs.test_ext.TestExt2
    tail output_folder/TestExt2-build.log

Fails with error in the log:

    mkfs.ext2: the -r option has been removed.

    If you really need compatibility with pre-1995 Linux systems, use the
    command-line option "-E revision=0".

Upstream commit [2] "tune2fs: replace the -r option with -E
revision=<fs-rev>" removed this option.

This commit fixes the issue by using the new form with -E. Also,
BR2_TARGET_ROOTFS_EXT2_MKFS_OPTIONS has a default value to "-O
^64bit". Passing a "-O ..." option now generates an error when a
ext2r0 filesystem is created (because this revision does not support
ext2 filesystem feature options). This commit sets this default value
only if BR2_TARGET_ROOTFS_EXT2_2r0 is not set.

Fixes: [3]

[1] https://gitlab.com/buildroot.org/buildroot/-/commit/db459859fa3c8fb7a2c0c8b8616637644d9c12bf
[2] https://git.kernel.org/pub/scm/fs/ext2/e2fsprogs.git/commit/?id=3fffe9dd6be5a5ed77755cf23c267b4afd1e7651
[3] https://gitlab.com/buildroot.org/buildroot/-/jobs/8830670170

Signed-off-by: Julien Olivain <ju.o@free.fr>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>

The config.txt of the Rasperry Pi's supporting Wi-Fi and Bluetooth (i.e.
zero W, zero 2 W, 3, and 4) switch the Bluetooth function to use the
mini-UART (ttyS0) and restore UART0 (ttyAMA0) over the GPIOs 14 and 15
(as per miniuart-bt-overlay.dts[1]). All of them turn "on" the parameter
krnbt to autoprobe the bluetooth driver.

According to the README.md, the dtparam krnbt is now defaulting to "on"
since linux-raspberrypi 6.1.y[2]; it was defaulting to "off" before[3].

This removes the dtparam=krnbt=on from these config.txt files since the
value set is actually the default value.

[1]: https://github.com/raspberrypi/linux/blob/rpi-6.1.y/arch/arm/boot/dts/overlays/miniuart-bt-overlay.dts
[2]: https://github.com/raspberrypi/linux/blob/rpi-6.1.y/arch/arm/boot/dts/overlays/README#L294-L296
[3]: https://github.com/raspberrypi/linux/blob/rpi-5.10.y/arch/arm/boot/dts/overlays/README#L213-L215

Signed-off-by: Gaël PORTAY <gael.portay+rtone@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

Signed-off-by: Gaël PORTAY <gael.portay+rtone@gmail.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

There is actually no need to have two hash files for the xilinx-prebuilt
package.  As long as the boot/xilinx-prebuilt/xilinx-prebuilt.hash contains
the hash value for the default version as well as any version used by a
xilinx board defconfig, a single hash file is all that is needed.

In the future, when bumping the defconfig files independently of the
xilinx-prebuilt default version, all that has to be done is the following
process.

Patch Series:
1. Add new version hash to boot/xilinx-prebuilt/xilinx-prebuilt.hash.
2. Bump board defconfigs to new version.
3. Bump xilinx-prebuilt default version.

For this reason, this patch merges the two xilinx-prebuilt.hash files and
removes the board/xilinx xilinx-prebuilt.hash file.

Signed-off-by: Neal Frager <neal.frager@amd.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

This patch bumps the default version of xilinx-prebuilt to
xilinx_v2024.2_update1.  For some reason, the original xilinx_v2024.2
release tag was missing the kria boards.  There is no difference between
the xilinx_v2024.2 and the xilinx_v2024.2_update1 release tags other than
the fact that the kria boards are included.

Now that the release tag includes all the boards, it is possible to bump
the default version from xilinx_v2024.1 to xilinx_v2024.2_update1.

Signed-off-by: Neal Frager <neal.frager@amd.com>
Reviewed-by: Brandon Maier <brandon.maier@gmail.com>
Reviewed-by: Luca Ceresoli <luca.ceresoli@bootlin.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
--

Bump the versal defconfigs to use the xilinx-prebuilt xilinx_v2024.2_update1
release tag instead of the xilinx_v2024.2 release tag.

The zynqmp defconfigs are now using xilinx-embeddedsw for building the zynqmp
pmufw, so unlike versal, the zynqmp defconfigs no longer use xilinx-prebuilt.

Signed-off-by: Neal Frager <neal.frager@amd.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

Now that the versal defconfigs have been bumped to the new default version
xilinx_v2024.2_update1, the xilinx_v2024.2 hash can be removed.

Signed-off-by: Neal Frager <neal.frager@amd.com>
Signed-off-by: Arnout Vandecappelle <arnout@mind.be>

cuserid is deprecated and breaks the compilation on some new toolchains.
This patch fixes this issue.

Fixes:
    #81

Signed-off-by: Thomas Bonnefille <thomas.bonnefille@bootlin.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>